You can do some CM in terraform also. You can do remote exec after it finishes like this:

provisioner "file" { source = "file.config" destination = "/etc/configs/file.confg" }

'You can ouput info for Ansible (or others) from Terraform after it finishes. For example:

provisioner "local-exec" { command = "echo ${aws_instance.example.public_dns} >> inventory" } ouput "name" { value = "${aws_instance.example.public_dns}" }

@dashrender said in Getting Started with LXD on Ubuntu 17.04:

@scottalanmiller said in Getting Started with LXD on Ubuntu 17.04:

@dashrender said in Getting Started with LXD on Ubuntu 17.04:

@scottalanmiller said in Getting Started with LXD on Ubuntu 17.04:

@black3dynamite said in Getting Started with LXD on Ubuntu 17.04:

@scottalanmiller
Are you running KVM and LXD on the same machine?

I am, yes.

Wouldn't this be the expectation? in many if not most cases?

If you know my particular case, yes it would be an expectation. In a more common scenario, no, not so much.

Wouldn't you typically have LXD on a hypervisor?

LXD is a Type-C hypervisor, so while having it on top of a Type 1 is common, having it on bare metal is also common.

@stacksofplates That's what i loked about it while reading on it.

it makes even more sense in virtualized environments. One can easily add more RAM or disk space if required on VM. No need to dedicate partition for it.

1.4GB of downloads for this update!!